Skip to content

Consider property path root in QuerydslBindings #2422

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from

Conversation

mp911de
Copy link
Member

@mp911de mp911de commented Jul 29, 2021

We now consider a qualified property path when registering and querying QuerydslBindings to ensure that paths matching various domain types do not accidentally get applied for a different type than they were registered for.
Previously, a binding for Address.description would be also applied to User.description as only the property path description was considered when looking up bindings.

Closes #2418

mp911de added 2 commits July 29, 2021 09:09
We now consider a qualified property path when registering and querying `QuerydslBindings` to ensure that paths matching various domain types do not accidentally get applied for a different type than they were registered for.
Previously, a binding for `Address.description` would be also applied to `User.description` as only the property path `description` was considered when looking up bindings.

Closes #2418
@mp911de mp911de requested a review from odrotbohm July 29, 2021 09:49
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Jul 29, 2021
christophstrobl pushed a commit that referenced this pull request Sep 14, 2021
We now consider a qualified property path when registering and querying `QuerydslBindings` to ensure that paths matching various domain types do not accidentally get applied for a different type than they were registered for.
Previously, a binding for `Address.description` would be also applied to `User.description` as only the property path `description` was considered when looking up bindings.

Closes: #2418
Original Pull Request: #2422
christophstrobl pushed a commit that referenced this pull request Sep 14, 2021
We now consider a qualified property path when registering and querying `QuerydslBindings` to ensure that paths matching various domain types do not accidentally get applied for a different type than they were registered for.
Previously, a binding for `Address.description` would be also applied to `User.description` as only the property path `description` was considered when looking up bindings.

Closes: #2418
Original Pull Request: #2422
@christophstrobl christophstrobl deleted the issue/2418-querydsl-predicate-builder-cache-fix branch September 14, 2021 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: waiting-for-triage An issue we've not yet triaged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

QuerydslPredicateBuilder and QuerydslBindings do not consider owning type
3 participants